The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
eslint-config	Ready	Preview	Comment	Oct 21, 2025 6:01am

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

PR Review: Changesets Release PR

Summary

This is an automated release PR generated by the Changesets action to publish @mheob/[email protected]. The changes look good overall.

Code Quality ✅

Strengths:

• Clean automated changeset workflow - the PR correctly removes the consumed changeset file
• Proper semver bump (patch version for the React ESLint rules update)
• Changelog entry is well-formatted and includes proper attribution
• Version bump in package.json is accurate (8.14.3 → 8.14.4)

Best Practices ✅

The PR follows the repository's conventions:

• Conventional commits pattern used (chore(release):)
• Changesets workflow properly integrated
• No manual intervention needed in the automated files

Potential Issues 🔍

None identified - This is a standard automated release PR with the expected structure.

Underlying Changes Review (from PR #315)

Since this releases changes from #315, I reviewed those as well:

Positive changes:

• Re-enabled important React JSX rules that were incorrectly disabled (jsx-no-duplicate-props, jsx-uses-react, jsx-uses-vars)
• Consolidated duplicate rules (no-comment-textnodes → jsx-no-comment-textnodes)
• Fixed plugin name in comment (eslint-plugin-react-x)
• Removed unused Husky post-merge hook

Minor observation:

• The rule react/no-misused-capture-owner-stack was removed - if this was intentional (e.g., deprecated or causing issues), that's fine. Otherwise, consider documenting why it was removed.

Security Concerns ✅

No security issues identified. This is a configuration package release with no runtime code changes.

Performance Considerations ✅

No performance impact - these are ESLint configuration changes that affect linting time, not runtime performance.

Recommendation

✅ APPROVED - Safe to merge when ready to publish the new version to npm.

The automated release workflow is functioning correctly, and the underlying changes improve the React ESLint configuration by re-enabling important rules and cleaning up the configuration.